graceful-stop and rotatelogs

graceful-stop and rotatelogs

am 30.09.2009 19:16:41 von Paul Silevitch

--001485e7e7d8c28f590474ceb192
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I noticed the following warning text in the graceful-stop section of the
apache manual (http://httpd.apache.org/docs/2.2/stopping.html):

"You should also be wary of other potential race conditions, such as using
rotatelogs style piped logging. Multiple running instances of rotatelogs
attempting to rotate the same logfiles at the same time may destroy each
other's logfiles."

The only solution to the above race condition that I came up with was to
give the log file a unique name during startup (using a block). Is
anyone else using graceful-stop and rotatelogs? If so, what are you doing
to handle this race condition?

Thanks in advance,

Paul

--001485e7e7d8c28f590474ceb192
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

I noticed the following warning text in t=
he graceful-stop section of the apache manual ( he.org/docs/2.2/stopping.html">http://httpd.apache.org/docs/ 2.2/stopping.ht=
ml
):


"You should also be wary of other potential race c=
onditions, such as using rotatelogs style piped logging. Multiple running i=
nstances of rotatelogs attempting to rotate the same logfiles at the same t=
ime may destroy each other's logfiles."


The only solution to the above race=A0condition that I =
came up with was to give the log file a unique name=A0during startup=A0(usi=
ng a <perl> block). =A0Is anyone else using graceful-stop and rotatel=
ogs? =A0If so, what are you doing to handle this race condition?


Thanks in advance,

Paul
<=
div>



--001485e7e7d8c28f590474ceb192--